巴西专利BR112020005692A2 header formats in wireless communication

专利PDF首页>>巴西专利

专利附录

专利说明

权利要求

类似技术

同族专利

引用文献

法律状态

优先权

专利摘要:
Aspects of the present disclosure relate to methods and devices for wireless communication using a protocol data unit (PDU) including a service data adaptation protocol (SDAP) PDU that has an unencrypted header. The unencrypted SDAP header facilitates various optimizations in wireless communication.
公开号:BR112020005692A2
申请号:R112020005692-8
申请日:2018-08-21
公开日:2020-10-20
发明作者:Yue Yang；Shailesh Maheshwari；Aziz Gholmieh；Srinivasan Balasubramanian；Xing Chen；Arnaud Meylan
申请人:Qualcomm Incorporated；
IPC主号:

专利说明:

[0001] [0001] This application claims priority to and the benefit of US Provisional Patent Application No. 62 / 564,113 filed with the United States Patent and Trademark Office on September 27, 2017, and US Non-Provisional Patent Application No. 16 / 105,885 filed. at the United States Patent and Trademark Office on August 20, 2018, the entire content of which is incorporated herein by reference as if completely presented below in its entirety and for all applicable purposes. TECHNICAL FIELD
[0002] [0002] The technology discussed below generally refers to wireless communication systems, and more particularly, to a network protocol stack and header formats for wireless communication. INTRODUCTION
[0003] [0003] In wireless communication, a device can process data for transmission over a network protocol stack including multiple protocol layers. For example, the protocol stack can include a packet data compression protocol layer (PDCP), a radio link control layer (RLC), a media access control layer (MAC), and a layer physical (PHY). The MAC layer can select the modulation and encoding scheme (MCS) that configures the PHY layer. A service data unit (SDU) is a term used to refer to a data unit that is passed from an upper protocol layer to a lower protocol layer. For example, the
[0004] [0004] The following is a simplified summary of one or more aspects of this disclosure, in order to provide a basic understanding of such aspects. This summary is not a comprehensive overview of all the features covered in the disclosure and is not intended to identify key or critical elements of all aspects of the disclosure, nor to outline the scope of one or all aspects of the disclosure. Its sole purpose is to present some concepts of one or more aspects of the disclosure in a simplified way as a prelude to the more detailed description that will be presented later.
[0005] [0005] One aspect of the present disclosure provides a method of wireless communication on a transmission device. The transmission device receives one or more quality of service flows (QoS) from a protocol layer. A QoS flow can be an Internet Protocol (IP) flow that is identified to receive a quality of service treatment by the system. The transmitting device maps the one or more QoS streams to one or more data radio carriers (DRBs) established between the transmitting device and a receiving device. The transmitting device transmits a plurality of media access control (MAC) protocol data units (PDUs) corresponding to one or more DRBs or QoS streams. Each MAC PDU includes a data compression protocol PDU. packet (PDCP) that includes a PDCP header and a partially encrypted PDCP payload. In one example, the partially encrypted PDCP payload includes a service data adaptation protocol (SDAP) header that is unencrypted.
[0006] [0006] Another aspect of the present disclosure provides a method of wireless communication on a receiving device. The receiving device receives a MAC PDU including a PDCP PDU that includes a PDCP header and a partially encrypted PDCP payload. The receiving device extracts an SDAP PDU corresponding to one or more QoS streams, from the partially encrypted PDCP payload. The receiving device reads an SDAP header from the SDAP PDU to obtain information on one or more QoS streams before deciphering an SDAP payload from the SDAP PDU.
[0007] [0007] Another aspect of the present disclosure provides an apparatus for wireless communication. The device includes a memory that stores executable code, a transceiver configured for wireless communication, and a processor communicatively coupled with the memory and the transceiver. The processor and memory are configured to receive one or more QoS streams from a protocol layer. The processor and memory are further configured to map one or more QoS streams to one or more DRBs established between the device and a receiving device. The processor and memory are further configured to transmit a plurality of MAC PDUs corresponding to one or more DRBs. Each MAC PDU includes a PDCP PDU including a PDCP header and a partially encrypted PDCP payload. In one example, the partially encrypted PDCP payload includes an SDAP header that is unencrypted.
[0008] [0008] Another aspect of the present disclosure provides an apparatus for wireless communication. The device includes a memory that stores executable code, a transceiver configured for wireless communication, and a processor communicatively coupled with the memory and the transceiver. The processor and memory are configured to receive a MAC PDU that includes a PDCP PDU including a PDCP header and a partially encrypted PDCP payload. The processor and memory are further configured to extract an SDAP PDU corresponding to one or more QoS streams from the partially encrypted PDCP payload. The processor and memory are further configured to read an SDAP header from the SDAP PDU to obtain information on one or more QoS streams before deciphering an SDAP payload from the SDAP.
[0009] [0009] These and other aspects of the invention will become more fully understood by reviewing the detailed description below. Other aspects, characteristics and modalities of the present invention will become evident to those skilled in the art, when reviewing the following description of specific exemplary modalities of the present invention in conjunction with the attached figures. Although the features of the present invention can be discussed in relation to certain embodiments and figures below, all of the embodiments of the present invention can include one or more of the advantageous features discussed here. In other words, while one or more modalities can be discussed as having certain advantageous characteristics, one or more of these characteristics can also be used according to the various modalities of the invention discussed here. Similarly, although exemplary modalities can be discussed below as device, system or method modalities, it should be understood that such exemplary modalities can be implemented in various devices, systems and methods. BRIEF DESCRIPTION OF THE DRAWINGS
[0010] [0010] Figure 1 is a schematic illustration of a wireless communication system.
[0011] [0011] Figure 2 is a conceptual illustration of an example of a radio access network.
[0012] [0012] Figure 3 is a schematic illustration of exemplary independent partitions according to some aspects of disclosure.
[0013] [0013] Figure 4 is a diagram illustrating a user plan protocol stack for wireless communication according to some aspects of the disclosure.
[0014] [0014] Figure 5 is a diagram illustrating a PDU session established between a UE, a gNB, and a user plan function (UPF) according to some aspects of the disclosure.
[0015] [0015] Figure 6 is a diagram illustrating an exemplary MAC protocol data unit (PDU) according to some aspects of the disclosure.
[0016] [0016] Figure 7 is a block diagram that conceptually illustrates an example of a hardware implementation for a programming entity according to some aspects of the disclosure.
[0017] [0017] Figure 8 is a block diagram that conceptually illustrates an example of a hardware implementation for an entity programmed according to some aspects of the disclosure.
[0018] [0018] Figure 9 is a flow chart illustrating an exemplary process for wireless communication on a transmission device using a packet structure with an unencrypted service data adaptation protocol (SDAP) header according to some aspects of present disclosure.
[0019] [0019] Figure 10 is a flow chart illustrating an exemplary process for forming a MAC PDU with an unencrypted SDAP header in accordance with some aspects of the present disclosure.
[0020] [0020] Figure 11 is a diagram that illustrates an encryption process and a decryption process according to some aspects of the disclosure.
[0021] [0021] Figure 12 is a flow chart illustrating an exemplary process for wireless communication on a receiving device using a packet structure with an unencrypted SDAP header in accordance with some aspects of the present disclosure. DETAILED DESCRIPTION
[0022] [0022] The detailed description set out below in connection with the accompanying drawings is intended to be a description of various configurations and is not intended to represent the only configurations in which the concepts described here can be practiced. The detailed description includes specific details in order to provide a complete understanding of various concepts. However, it will be evident to people skilled in the art that these concepts can be practiced without these specific details. In some cases, known structures and components are shown in the form of a block diagram to avoid obscuring such concepts.
[0023] [0023] Although aspects and modalities are described in this application by way of illustration to some examples, people skilled in the art will understand that additional implementations and use cases can occur in many different arrangements and scenarios. The innovations described here can be implemented on many different types of platforms, devices, systems, shapes, sizes, packaging arrangements. For example, modalities and / or uses can occur through integrated modalities of chip and other devices based on non-modular components (eg, end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail devices / purchases, medical devices, AI-enabled devices, etc.). Although some examples may or may not be specifically targeted to use cases or applications, there may be a wide range of applicability of the innovations described. The implementations can cover a spectrum of modular or chip-level components to non-modular and chip-level implementations, in addition to aggregated, distributed or OEM devices or systems, incorporating one or more aspects of the described innovations. In some practical configurations, devices that incorporate aspects and features described may also necessarily include additional components and resources for implementing and practicing claimed and described modalities. For example, wireless signal transmission and reception necessarily includes several components for analog and digital purposes (for example, hardware components, including antenna, RF currents, power amplifiers, modulators, buffer, processor (s), interleaver, adder / adder, etc.) It is intended that the innovations described here can be practiced on a wide variety of devices, components at the chip level, systems, distributed arrangements, end-user devices, etc. of varying sizes, shapes and constitutions.
[0024] [0024] Aspects of the present disclosure provide a data packet format that can facilitate certain optimizations in wireless communication using a layered protocol stack. Some examples of such optimizations include data prioritization during transmission and packet pre-processing during reception.
[0025] [0025] The various concepts presented throughout this disclosure can be implemented through a wide variety of telecommunications systems, network architectures, and communication standards. Referring now to Figure 1, as an illustrative example without limitation, several aspects of the present disclosure are illustrated with reference to a wireless communication system 100. Wireless communication system 100 includes three domains of interaction: a main network 102, a radio access network (RAN) 104, and user equipment (UE) 106. Due to the wireless communication system 100, the UE 106 can be enabled to carry out data communication with an external data network 110, like (but not limited to) the Internet.
[0026] [0026] RAN 104 may implement any appropriate wireless communication technology or technologies to provide radio access to the UE 106. As an example, RAN 104 may operate in accordance with the Nova Radio (NR) specifications of the 3rd Generation Partnership (3GPP), often referred to as 5G. As another example, RAN 104 can operate under a hybrid of 5G NR and evolved Universal Terrestrial Radio Access Network (eUTRAN) standards, often referred to as LTE. 3GPP refers to this hybrid RAN as a next generation RAN, or NG RAN. Certainly, many other examples can be used within the scope of this disclosure.
[0027] [0027] As illustrated, RAN 104 includes a plurality of base stations 108. In general terms, a base station is a network element in a radio access network responsible for radio transmission and reception in one or more cells to or of an UE. In different technologies, patterns, or contexts, a base station can be differently referred to by the person skilled in the art as a base transceiver (BTS), a radio base station, a radio transceiver, a transceiver function, a basic set service (BSS), an extended service set (ESS), an access point (AP), a Node B (NB), an eNode B (eNB), a gNode B (gNB), or some other suitable terminology.
[0028] [0028] The radio access network 104 is further illustrated by supporting wireless communication for various mobile devices. A mobile device can be referred to as user equipment (UE) in 3GPP standards, but it can also be referred to by the person skilled in the art as a mobile station (MS), a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal (AT), a mobile terminal, a mobile terminal , a wireless terminal, a remote terminal, a telephone, a terminal, a user agent, a mobile client, a client or some other suitable terminology. A UE can be a device that provides the user with access to network services.
[0029] [0029] Within the present document, a "mobile" device does not necessarily need to be able to move, and can be stationary.
[0030] [0030] Wireless communication between a RAN 104 and a UE 106 can be described as using an overhead interface. Transmissions over the air interface from a base station (e.g., base station 108) to one or more UEs (e.g., UE 106) can be termed as downlink (DL) transmission. According to certain aspects of the present disclosure, the term downlink can refer to a transmission from point to multipoint originating in a programming entity (described below; for example, base station 108). Another way to describe this scheme can be to use the term multiplexing of the broadcast channel. Transmissions from a UE (e.g., UE 106) to a base station (e.g., base station 108) can be termed as uplink (UL) transmissions. In accordance with other aspects of this disclosure, the term uplink can refer to a point-to-point transmission originating in a programmed entity (described further below; for example, UE 106).
[0031] [0031] In some examples, access to the air interface can be programmed, in which a programming entity (for example, a base station 108) allocates resources for communication between some or all devices and equipment within its area or service cell . Within this disclosure, as discussed below, the programming entity may be responsible for programming, assigning, reconfiguring, and releasing resources to one or more programmed entities. That is, for programmed communication, UEs 106, which can be programmed entities, can use resources allocated by the programming entity 108.
[0032] [0032] Base stations 108 are not the only entities that can function as programming entities. That is, in some examples, a UE can function as a programming entity, programming resources for one or more programmed entities (for example, one or more other UEs).
[0033] [0033] As illustrated in Figure 1, a programming entity 108 can broadcast downlink traffic 112 to one or more programmed entities 106. In general terms, programming entity 108 is a node or device responsible for scheduling traffic on a network. wireless communication, including downlink traffic 112 and, in some instances, uplink traffic 116 from one or more programmed entities 106 to programming entity 108. On the other hand, programmed entity 106 is a node or device that receives information downlink control 114, including but not limited to programming information (for example, a lease), synchronization or timing information, or other control information from another entity on the wireless communication network such as programming entity 108.
[0034] [0034] In general, base stations 108 may include a backhaul interface for communication with a backhaul portion 120 of the wireless communication system. Backhaul 120 can provide a link between a base station 108 and main network 102. In addition, in some examples, a backhaul network can provide interconnection between the respective base stations 108. Various types of backhaul interfaces can be used, such as a direct physical connection, a virtual network, or the like using any suitable transport network.
[0035] [0035] Main network 102 can be a part of wireless communication system 100, and can be independent of radio access technology used in RAN
[0036] [0036] Referring now to Figure 2, by way of example and without limitation, a schematic illustration of a RAN 200 is provided. In some examples, the RAN 200 can be the same as the RAN 104 described above and illustrated in Figure 1. The geographical area covered by the RAN 200 can be divided into cellular regions (cells) that can be identified exclusively by user equipment ( UE) based on an identification transmitted from an access point or base station. Figure 2 illustrates macrocells 202, 204 and 206 and a small cell 208, each of which may include one or more sectors (not shown). A sector is a subarea of a cell. All sectors in a cell are served by the same base station. A radio link within a sector can be identified by a unique logical identification pertaining to that sector. In a cell that is divided into sectors, the multiple sectors within a cell can be formed by groups of antennas with each antenna responsible for communicating with UEs in a portion of the cell.
[0037] [0037] In Figure 2, two base stations 210 and 212 are shown in cells 202 and 204; and a third base station 214 is shown controlling a remote radio head (RRH) 216 in cell 206. That is, a base station can have an integrated antenna or can be connected to an antenna or RRH by feeder cables. In the illustrated example, cells 202, 204 and 126 can be referred to as macrocells, as base stations 210, 212 and 214 support cells with a large size. In addition, a base station 218 is shown in small cell 208 (for example, a microcell, peak cell, femto cell, initial base station, domestic node B, domestic eNode B, etc.) that can overlap with one or more macrocells . In this example, cell 208 can be referred to as a small cell, as base station 218 supports a cell of relatively small size. The dimensioning of the cells can be done according to the system design, as well as the restrictions of the components.
[0038] [0038] It should be understood that the radio access network 200 can include any number of base stations and wireless cells. In addition, a relay node can be deployed to extend the size or area of coverage of a given cell. Base stations 210, 212, 214, 218 provide wireless access points to a primary network for any number of mobile devices. In some examples, the base stations 210, 212, 214 and / or 218 may be the same as the base station / programming entity 108 described above and illustrated in Figure 1.
[0039] [0039] Figure 2 also includes a quadcopter or drone 220, which can be configured to function as a base station. That is, in some instances, a cell may not necessarily be stationary, and the cell's geographic area may move according to the location of a mobile base station such as quadricopter 220.
[0040] [0040] Within the RAN 200, cells can include UEs that can be in communication with one or more sectors of each cell. In addition, each base station 210, 212, 214, 218, and 220 can be configured to provide an access point for a main network 102 (see, Figure 1) for all UEs in the respective cells. For example, UEs 222 and 224 may be in communication with base station 210; UEs 226 and 228 may be in communication with base station 212; UEs 230 and 232 may be in communication with base station 214 via RRH 216; UE 234 may be in communication with base station 218; and UE 236 may be in communication with mobile base station 220. In some examples, UEs 222, 224, 226, 228, 230, 232, 234, 236, 238, 240, and / or 242 may be the same as the UE / programmed entity 106 described above and illustrated in Figure 1.
[0041] [0041] In some examples, a mobile network node (for example, quadcopter 220) can be configured to function as a UE. For example, quadcopter 220 can operate within cell 202 communicating with base station 210.
[0042] [0042] In another aspect of the RAN 200, side link signals can be used between the UEs without necessarily relaying control information or programming from a base station. For example, two or more UEs (for example, UEs 226 and 228) can communicate with each other using point-to-point (P2P) or side-link signals 227 without relaying that communication through a base station (for example, base station 212 ). In another example, UE 238 is illustrated by communicating with UEs 240 and 242. Here, UE 238 can function as a programming entity or a primary side link device, and UEs 240 and 242 can function as a programmed entity or a non-primary (for example, secondary) side link device. In yet another example, a UE may function as a device-to-device (D2D), point-to-point (P2P) or vehicle to vehicle network programming entity, and / or on a mesh network. In an example of a mesh network, UEs 240 and 242 can optionally communicate directly with each other in addition to communicating with the programming entity
[0043] [0043] In the radio access network 200, the ability of a UE to communicate while moving, regardless of its location, is called mobility. The various physical channels between the UE and the radio access network are generally configured, maintained and released under the control of an access and mobility management function (MFA, not shown, part of the main network 102 in Figure 1), which it can include a security context management (SCMF) function that manages the security context for the control plan and user plan functionality and a security anchor function (SEAF) that performs authentication.
[0044] [0044] In various aspects of disclosure, a radio access network 200 can use DL-based mobility or UL-based mobility to allow mobility and transfers (i.e. transferring a UE connection from a radio channel to another). In a network configured for DL-based mobility, during a call with a scheduling entity, or at any other time, a UE can monitor various parameters of its service cell signal, as well as several parameters of neighboring cells. Depending on the quality of these parameters, the UE can maintain communication with one or more of the neighboring cells. During that time, if the UE moves from one cell to another, or if the signal quality of a neighboring cell exceeds that of the serving cell for a certain period of time, the UE can perform a transfer or transfer from the service cell to the neighboring (target) cell. For example, UE 224 (illustrated as a vehicle, although any suitable form of UE can be used) can move from the geographic area corresponding to its service cell 202 to the geographic area corresponding to a neighboring cell 206. When the intensity or signal quality of neighboring cell 206 exceeds that of its service cell 202 for a certain period of time, UE 224 may transmit a report message to its service base station 210 indicating this condition. In response, UE 224 can receive a transfer command, and the UE can be transferred to cell 206.
[0045] [0045] In a network configured for UL-based mobility, the UL reference signals from each UE can be used by the network to select a service cell for each UE. In some examples,
[0046] [0046] Although the synchronization signal transmitted by base stations 210, 212, and 214/216 can be unified, the synchronization signal may not identify a specific cell, but may identify a zone of several cells operating on the same frequency and / or with the same timing. The use of zones on 5G networks or other next generation communication networks allows for uplink-based mobility structure and improves the efficiency of the UE and the network, since the number of mobility messages that need to be exchanged between the UE and the network can be reduced.
[0047] [0047] In various implementations, the air interface in the radio access network 200 can use licensed spectrum, unlicensed spectrum or shared spectrum. The licensed spectrum provides for the exclusive use of part of the spectrum, usually due to a mobile network operator acquiring a license from a government regulator. The unlicensed spectrum allows for the shared use of a part of the spectrum without the need for a license granted by the government. Although compliance with some technical rules is still generally required to access the unlicensed spectrum, generally any operator or device can gain access. The shared spectrum can fall between licensed and unlicensed spectrum, where technical rules or limitations may be required to access the spectrum, but the spectrum can still be shared by multiple operators and / or multiple RATs. For example, a license holder for a part of the licensed spectrum may provide licensed shared access (LSA) to share that spectrum with other parties, for example, under appropriate conditions and determined by the licensee to obtain access.
[0048] [0048] The aerial interface in the radio access network 200 may use one or more duplexing algorithms. Duplex refers to a point-to-point communication link where the two endpoints can communicate with each other in both directions. Full-duplex means that the two endpoints can communicate simultaneously. Half-duplex means that only one terminal can send information to the other at a time. On a wireless link, a full-duplex channel generally depends on the physical isolation of a transmitter and receiver and on appropriate interference cancellation technologies. Full duplex emulation is often implemented for wireless links using frequency division duplex (FDD) or time division duplex (TDD). In FDD, transmissions in different directions operate on different carrier frequencies. In TDD, transmissions in different directions on a given channel are separated from one another using time division multiplexing. That is, sometimes the channel is dedicated for transmissions in one direction, while other times the channel is dedicated for transmissions in the other direction, where the direction can change very quickly, for example, several times per partition.
[0049] [0049] In order, for transmissions through the radio access network 200 to obtain a low block error rate (BLER) while still reaching very high data rates, channel encoding can be used. That is, wireless communication can generally use an appropriate error correction block code. In a typical block code, a message or sequence of information is divided into code blocks (CBs) and an encoder (for example, a CODEC) on the transmitting device then mathematically adds redundancy to the information message. The exploitation of this redundancy in the coded information message can improve the reliability of the message, allowing the correction of any bit errors that may occur due to noise.
[0050] [0050] In the initial specifications of NR 5G, user data is encoded using the almost cyclic low density parity check (LDPC) with two different basic graphs: a basic graph is used for large blocks of code and / or high rates code, while the other otherwise, the base chart. Control information and the physical transmission channel (PBCH) are encoded using polar encoding, based on nested strings. For these channels, puncture, shortening and repetition are used for rate matching.
[0051] [0051] However, persons of ordinary skill in the art will understand that aspects of the present disclosure can be implemented using any suitable channel code. Various implementations of programming entities 108 and programmed entities 106 may include suitable hardware and resources (for example, an encoder, a decoder and / or a CODEC) to use one or more of these channel codes for wireless communication.
[0052] [0052] The aerial interface in the radio access network 200 may use one or more multiplexing and multiple access algorithms to allow simultaneous communication of the various devices. For example, NR 5G specifications provide multiple access for UL transmissions from UEs 222 and 224 to base station 210 and for multiplexing for DL transmissions from base station 210 to one or more UEs 222 and 224, using division multiplexing orthogonal frequency (OFDM) with a cyclic prefix (CP). In addition, for UL transmissions, the NR 5G specifications provide support for discrete OFDM of Fourier expansion transformation (DFT-s-OFDM) with a CP (also known as single carrier FUMA (SC-FDMA)). However, within the scope of this disclosure, multiplexing and multiple access are not limited to the above schemes, and can be provided using time division multiple access (TDMA), code division multiple access (CDMA), access frequency division multiple (FDMA), sparse code multiple access (SCMA), resource spread multiple access (RSMA) or other suitable multiple access schemes. In addition, multiplexing DL transmissions from base station 210 to UEs 222 and 224 can be provided using time division multiplexing (TDM), code division multiplexing (CDM), frequency division multiplexing (FDM), orthogonal frequency division multiplexing (OFDM), sparse code multiplexing (SCM) or other suitable multiplexing schemes.
[0053] [0053] Within the present disclosure, a frame can refer to a duration of a predetermined duration (for example, 10 ms) for wireless transmissions, with each frame consisting of a predetermined number of subframes (for example, 10 subframes of 1 ms each). On a given carrier, there may be one set of frames on the UL and another set of frames on the DL. Each subframe can consist of one or more adjacent partitions. In some examples, a partition can be defined according to a specified number of OFDM symbols with a given cyclic prefix length (CP). For example, a partition can include 7 or 14 OFDM symbols with a nominal CP. Additional examples may include mini-partitions with a shorter duration (for example, one or two OFDM symbols). These mini-partitions can in some cases be transmitted using resources programmed for partition transmissions in progress to the same or to different UEs. An example partition can include a control region and a data region. In general, the control region can carry control channels and the data region can carry data channels. Obviously, a partition can contain all DL, all UL or at least a portion of DL and at least a portion of UL. In some aspects of disclosure, different slot structures may be used and may include one or more of each of the control regions and data region (s).
[0054] [0054] In a DL transmission, the transmitting device (for example, programming entity 108) can allocate one or more resource elements (REs) (for example, time frequency resources within a control region) to carry DL 114 control information, including one or more DL control channels, such as a PBCH; a PSS; an SSS; a physical control format indicator channel (PCFICH); a physical auto-repeat request (HARQ) indicator channel (PHICH); and / or a physical downlink control channel (PDCCH), etc., for one or more programmed entities 106. The PCFICH provides information to assist a receiving device in receiving and decoding the PDCCH. The PDCCH carries downlink control information (DCI), including, but not limited to, power control commands, programming information, a grant and / or an assignment of REs for DL and UL transmissions. PHICH carries HARQ feedback streams, such as acknowledgment (ACK) or negative acknowledgment (NACK). HARQ is a technique well known to those skilled in the art, in which the integrity of packet transmissions can be checked on the receiving side for accuracy, for example, using any suitable health check mechanism, such as a checksum or a check of cyclic redundancy (CRC). If the integrity of the transmission is confirmed, an ACK can be transmitted, while, if not confirmed, a NACK can be transmitted. In response to a NACK, the transmitting device can send a HARQ retransmission, which can implement a combination of chase, incremental redundancy, etc.
[0055] [0055] In a UL transmission, the transmission device (for example, programmed entity 106) can use one or more REs to carry UL 118 control information including one or more UL control channels, such as a transmission channel. physical uplink control (PUCCH), for programming entity 108. UL control information can include a variety of package types and categories, including pilots, reference signals, and information configured to enable or assist in decoding transmissions uplink data. In some examples, control information 118 may include a scheduling request (SR), for example, a request for scheduling entity 108 to schedule uplink transmissions. Here, in response to the SR transmitted on the control channel 118, the programming entity 108 can transmit downlink control information 114 which can program resources for uplink packet transmissions. UL control information may also include HARQ feedback, channel status feedback (CSF), or any other appropriate UL control information.
[0056] [0056] In addition to control information, one or more REs (for example, within the data region) can be allocated for user data or traffic data. Such traffic can be carried on one or more traffic channels, such as, for a DL transmission, a physical downlink shared channel (PDSCH); or for a UL broadcast, a shared physical uplink (PUSCH) channel. In some examples, one or more REs within the data region can be configured to carry system information blocks (SIBs), carrying information that can allow access to a particular cell.
[0057] [0057] The channels or carriers described above and illustrated in Figure 1 are not necessarily all channels or carriers that can be used between a programming entity 108 and programmed entities 106, and persons of ordinary skill in the art will recognize that other channels or carriers can be used in addition to those illustrated, such as other traffic, control, and feedback channels.
[0058] [0058] These physical channels described above are usually multiplexed and mapped to carry channels for manipulation in the medium access control layer (MAC). Transport channels carry blocks of information called transport blocks (TB). The transport block size (TBS), which can correspond to a number of bits of information, can be a controlled parameter, based on the modulation and coding scheme (MCS) and the number of RBs in a given transmission.
[0059] [0059] According to one aspect of the disclosure, one or more partitions can be structured as independent partitions. For example, Figure 3 illustrates two examples of independent partition structures 300 and 350. Independent partitions 300 and / or 350 can be used, in some examples, in wireless communication between a programming entity 108 and a programmed entity
[0060] [0060] In the illustrated example, a centered partition of DL 300 can be a partition programmed by the transmitter. DL centered nomenclature generally refers to a structure in which more resources are allocated for transmissions in the direction of DL (for example, transmissions from programming entity 108 to programmed entity 106). Likewise, a centered partition of UL 350 can be a partition programmed by the receiver, where more resources are allocated for transmissions towards the UL (for example, transmissions from programmed entity 106 to programming entity 108).
[0061] [0061] Each partition, like the independent partitions 300 and 350, can include portions of transmission (Tx) and reception (Rx). For example, in the centered partition of DL 300, programming entity 108 first has an opportunity to transmit control information, for example, on a PDCCH, in a DL 302 control region, and then an opportunity to transmit data or DL user traffic, for example, on a PDSCH in a DL 304 data region. After a guard period (GP) region 306 having an appropriate duration 310, programming entity 108 has an opportunity to receive data UL and / or UL feedback including any programming requests from UL, CSF, an ACK / NACK from HARQ, etc., in a burst of UL 308 from other entities using the carrier. Here, a partition such as the centered partition of DL 300 can be termed as an independent partition when all data transported in data region 304 is in control region 302 of the same partition; and furthermore, when all data carried in the 304 data region is recognized (or at least has an opportunity to be recognized) in the UL 308 burst of the same partition. In this way, each independent partition can be considered an independent entity, not necessarily requiring any other partition to complete a schedule transmission confirmation cycle for any given package.
[0062] [0062] The GP 306 region can be included to accommodate variability in UL and DL timing. For example, latencies due to directional switching of the radio frequency (RF) antenna (for example, from DL to UL) and transmission path latencies can cause programmed entity 106 to transmit early on UL to match DL timing. Such early transmission may interfere with symbols received from the programming entity 108. Consequently, the GP 306 region may allow an amount of time after the DL 304 data region prevents interference, where the GP 306 region provides an amount appropriate time for the programming entity 108 to switch its RF antenna direction, an appropriate amount of time for air transmission (OTA), and an appropriate amount of time for ACK processing by the programmed entity.
[0063] [0063] Likewise, the centered partition of UL 350 can be configured as an independent partition. The centered partition of UL 350 is substantially similar to the centered partition of DL 300, including a guard period 354, a data region of UL 356, and a burst region of UL 358.
[0064] [0064] The partition structure illustrated in partitions 300 and 350 is just one example of independent partitions. Other examples may include a common DL portion at the beginning of each partition, and a common UL portion at the end of each partition, with several differences in the partition structure between these respective portions. Other examples can still be provided within the scope of this disclosure.
[0065] [0065] Figure 4 is a diagram that illustrates a user plan protocol stack 400 for wireless communication according to some aspects of the disclosure. In some instances, this protocol stack 400 may be used on a Nova Radio 5G (NR) network between a programming entity 108 (eg, gNB) and a programmed entity 106 (eg, UE). In some examples, protocol stack 400 can be used among other devices. Protocol stack 400 includes a PHY 402 layer that implements several physical layer communication functions. Other protocol layers are a media access control layer (MAC) 404, a radio link control layer (RLC) 406, a packet data convergence protocol layer (PDCP) 408, and a layer of Service Data Adaptation Protocol (SDAP) 410. The services and functions of the SDAP 410 layer can include mapping between a QoS stream and a data carrier, and QoS stream ID (QFI) tagging and both packets. DL and UL. A QoS flow is one or more Internet Protocol (IP) flows that are identified to receive a quality of service treatment by the system. In one example, an IP stream can be IP traffic from one endpoint to another endpoint, and can be identified by the source and destination of IP addresses and ports as well as the transport protocol (UDP or TCP) . A single SDAP protocol entity can be configured for each individual PDU session. The PDCP 408 layer provides several functions including data encryption and decryption. Upstream of the SDAP 410 layer can be one or more upper layers, for example, an IP layer, and / or an application layer. Each protocol layer in programming entity 108 communicates with a corresponding pair protocol layer in programmed entity 106. In some examples, one or more of the protocol layers may not be used in a network entity.
[0066] [0066] Figure 5 is a diagram illustrating a PDU session established between an UE 502, a gNB 504, and a user plan function (UPF) 506 according to some aspects of the disclosure. In some examples, UE 502 can be any of the UEs or programmed entities illustrated in Figures 1, 2 and 4, and gNB 504 can be any of the base stations or programming entities illustrated in Figures 1, 2, and 4. In a 5G NR network, the main network can consist of several network functions (NFs). One of the NFs is an UPF 506 that connects the gNB 504 to a data network that provides access to the Internet or operator services. The UPF supports features and capabilities to facilitate the operation of the user plan, for example, routing and forwarding of packets, interconnection with the data network, application of policies and data buffering. In one example, the UPF 506 can reside on the main network 102. In some instances, more than one PDU session can be established for the UE 502. The
[0067] [0067] The SDAP 410 layer (see, Figure 4) can handle some of the mapping functions for the PDU session. For example, in the downlink, the SDAP layer 410 receives one or more flows of QoS 510 from the top layer (for example, an IP layer) and maps each flow of QoS to a corresponding DRB 508. In some examples, 510 QoS streams may have a different priority. The network ensures quality of service (for example, reliability, latency and destination delay) by mapping packets to appropriate QoS flows and DRBs. For example, latency-sensitive packets can be mapped to a higher priority QoS stream, while latency-sensitive packets can be mapped to a lower priority QoS stream. In the uplink, the SDAP 410 layer can provide reflective mapping. For example, the network can decide on the QoS for DL traffic, and the UE reflects or mirrors the QoS DL on the associated UL traffic. That is, the DL and UL can have the same QoS. The SDAP 410 layer marks the data packets for each QoS stream with a QoS stream ID (for example, QFI) in the DL and UL packets. For each DRB, the UE monitors the QFI (s)
[0068] [0068] Figure 6 is a diagram illustrating an exemplary MAC protocol data unit (PDU) 600 according to some aspects of the disclosure. The MAC 600 PDU can be used for wireless communication, for example, in the wireless communication system 100. The MAC 600 PDU includes several fields, for example, a MAC 602 header and a MAC 604 payload. MAC 604 payload can include various data from the upper network layers, for example, an RLC header 606, a PDCP header 608, an SDAP header 610, and an SDAP payload
[0069] [0069] In some examples, the SDAP 610 header can include information in a QFI 614 and a reflective QoS indicator (RQI) 616. The RQI can be set to a certain value (for example, 0 or 1) to indicate that some or all of the traffic carried in this QoS flow is subject to reflective mapping. In other examples, the SDAP 610 header may have other data fields not shown in Figure 6. In some examples, the QFI and RQI may be in different SDAP 610 header locations than shown in Figure 6.
[0070] [0070] In some aspects of the disclosure, one or more of the data fields of the MAC 600 PDU can be encrypted on the transmitting device and decrypted on the receiving device. For example, some systems or devices may consider all data fields that follow the PDCP 608 header (for example, SDAP 610 header and SDAP 612 payload) as a PDCP 618 payload, and therefore those systems or devices can encrypt and decrypt these PDCP payload data fields together. In this case, the SDAP 610 header is encrypted and decrypted along with the SDAP payload. In one example, the SDAP payload can be an IP payload. However, the encryption / decryption of the SDAP header can prevent some potential optimization implementations that can be used in an NR network.
[0071] [0071] In some aspects of disclosure, the SDAP 610 header may not be encrypted ("unencrypted"), while the SDAP payload (for example, IP payload) is encrypted when the SDAP 610 header is included on the MAC 600 PDU. Using an unencrypted SDAP header allows for certain optimizations in UL and DL communication, as described below.
[0072] [0072] Figure 7 is a block diagram illustrating an example of a hardware implementation for a programming entity 700 using a processing system 714. For example, programming entity 700 can be a user equipment (UE) as illustrated in any one or more of Figures 1, 2, and / or 4. In another example, the programming entity 700 may be a base station as illustrated in any one or more of Figures 1, 2, and / or 4 .
[0073] [0073] Programming entity 700 can be implemented with a processing system 714 that includes one or more processors 704. Examples of processors 704 include microprocessors, microcontrollers, digital signal processors (DSPs), field programmable port arrays (FPGAs) ), programmable logic devices (PLDs), state machines, blocked logic, discrete hardware circuits and other suitable hardware configured to perform the various features described throughout this release. In several examples, the programming entity 700 can be configured to perform any one or more of the functions described here. That is, processor 704, as used in a programming entity 700, can be used to implement any one or more of the processes and procedures described below and illustrated in Figures 9 to 12.
[0074] [0074] In this example, processing system 714 can be implemented with a bus architecture, generally represented by bus 702. Bus 702 can include any number of interconnecting buses and bridges, depending on the specific application of processing system 714 and o general design restrictions. The bus 702 communicates several circuits, including one or more processors (generally represented by the processor 704), a 705 memory and computer-readable media (generally represented by the computer-readable medium 706). The 702 bus can also connect several other circuits, such as timing sources, peripherals, voltage regulators and power management circuits, which are well known in the art and therefore will not be described further. A bus interface 708 provides an interface between bus 702 and a transceiver 710. Transceiver 710 provides an interface or means of communication for communicating with various other devices via a transmission means. Depending on the nature of the device, a 712 user interface (for example, keyboard, screen, speaker, microphone, joystick) may also be provided. Obviously, this 712 user interface is optional and can be omitted in some examples, such as a base station.
[0075] [0075] In some aspects of the disclosure, processor 704 may include circuitry configured for various functions, including, for example, a 740 processing circuit, an UL 742 communication circuit, and a DL communication circuit
[0076] [0076] Processor 704 is responsible for managing the 702 bus and general processing, including running the software stored in the computer-readable medium 706. The software, when run by the processor 704, makes the processing system 714 perform the various functions described below for any particular device. Computer-readable media 706 and memory 705 can also be used to store data that is handled by processor 704 when running the software.
[0077] [0077] One or more 704 processors in the processing system can run software. The software should be interpreted broadly as instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects , executables, threads of execution, procedures, functions, etc., called software, firmware, middleware, microcode, language of the hardware description or others. The software may reside on a computer-readable medium 706. The computer-readable medium 706 may be a non-transitory, computer-readable medium. A non-transitory computer-readable medium includes, for example, a magnetic storage device (for example, hard disk, floppy disk, magnetic tape), an optical disk (for example, a CD (CD) or a versatile digital disk ( DVD)), a smart card, a flash memory device (for example, a card, card or key unit), random access memory (RAM), read-only memory (ROM), programmable ROM ( PROM), an erasable PROM (EPROM), an electrically erasable PROM (EEPROM), a record, a removable disk and any other suitable means to store software and / or instructions that can be accessed and read by a computer. The computer-readable medium 706 can reside in the processing system 714, external to the processing system 714, or distributed by various entities, including the processing system 714. The computer-readable medium 706 can be incorporated into a computer program product . For example, a computer program product may include a computer-readable medium in packaging materials. People skilled in the art will recognize the best way to implement the described functionality presented throughout this disclosure, depending on the specific application and the general design restrictions imposed on the general system.
[0078] [0078] In one or more examples, the computer-readable storage medium 706 may include software configured for various functions, including, for example, 752 processing instructions, UL 754 communication instructions, and DL communication instructions
[0079] [0079] Figure 8 is a conceptual diagram illustrating an example of a hardware implementation for an exemplary programmed entity 800 using an 814 processing system. According to various aspects of the disclosure, an element, or any portion of an element, or any combination of elements can be implemented with an 814 processing system that includes one or more processors
[0080] [0080] The processing system 814 can be substantially the same as the processing system 714 illustrated in Figure 7, including a bus interface 808, an 802 bus, memory 805, a processor 804, and a computer-readable medium 806.
[0081] [0081] In some aspects of the disclosure, processor 804 may include circuitry configured for various functions, including, for example, a processing circuit 840, a communication circuit of DL 842, and a communication circuit of UL 844.
[0082] [0082] The processing circuit 840 can be configured to perform various functions of data processing and programming and allocation of communication resources. In one example, processing circuit 840 can be configured to implement several protocol entities including a PHY entity, a MAC entity, an RLC entity, a PDCP entity, and an SDAP entity. The UL 844 communication circuit can be configured to perform various UL communication functions, for example, encoding, encryption, multiplexing, and transmission. The DL 842 communication circuit can be configured to perform various DL communication functions, for example, decoding, decrypting, demultiplexing, and receiving. For example, the circuitry can be configured to implement one or more of the functions described in relation to Figures 9 to 12.
[0083] [0083] In one or more examples, the 806 computer-readable storage medium may include software configured for various functions, including, for example, 852 processing instructions, DL 854 communication instructions, and UL communication instructions
[0084] [0084] Figure 9 is a flow chart illustrating an exemplary process 900 for wireless communication on a transmission device using a packet structure with an unencrypted SDAP header in accordance with some aspects of the present disclosure. As described below, some or all of the illustrated features may be omitted in a specific implementation within the scope of this disclosure, and some illustrated features may not be required for the implementation of all modalities. In some examples, process 900 can be performed by programming entity 700 illustrated in Figure 7. In some examples, process 900 can be performed by programmed entity 800 illustrated in Figure 8. In some examples, process 900 can be performed by any suitable apparatus or means to carry out the functions or algorithms described below.
[0085] [0085] In block 902, the transmission device can receive one or more QoS streams from an application layer or IP layer that has data for transmission. In one aspect of the disclosure, an application layer or IP layer in the programming entity 108 or programmed entity 106 can transmit one or more QoS streams to the transmitting device. For example, the device can use processing circuit 740 (see, Figure 7) to implement an SDAP layer entity that receives QoS streams. QoS streams can have different levels of priority and / or latency requirement. For example, a QoS flow having a higher priority may have allocated more time and / or frequency resources.
[0086] [0086] In block 904, the transmitting device can map one or more QoS flows to one or more data radio carriers (DRBs) established between the transmitting device and a receiving device. In one example, the transmitting device can be a programming entity (for example, gNB), and the receiving device can be a programmed entity (for example, UE). In one example, the transmitting device can use the SDAP layer entity to map the one or more QoS streams to one or more DRBs.
[0087] [0087] In block 906, the transmission device can transmit a plurality of MAC protocol data units corresponding to the DRBs. Each MAC PDU includes a PDCP PDU including a PDCP header and a partially encrypted PDCP payload. In one aspect of the disclosure, the PDCP payload can be the same as the PDCP 618 payload shown in Figure 6. For example, the PDCP payload can include an SDAP header and an SDAP payload (for example , IP payload). The PDCP payload can be partially encrypted. For example, the SDAP header is unencrypted, while the SDAP payload is encrypted. In one example, the transmitting device can read the SDAP header from the partially encrypted PDCP payload to obtain SDAP payload prioritization information and to prioritize the transmission of the plurality of MAC PDUs based on the prioritization information. In one example, the SDAP header indicates a required QoS level for the packet, and the QoS level can be used to select a priority between packets for transmission. Likewise, the device can use the SDAP header of incoming packets to prioritize receipt through packets and forward to the host.
[0088] [0088] Figure 10 is a flow chart illustrating an exemplary process 1000 for forming a MAC PDU with an unencrypted SDAP header in accordance with some aspects of the present disclosure. In some examples, process 1000 can be performed by the programming entity 700 illustrated in Figure 7. In some examples, process 1000 can be performed by the programmed entity 800 illustrated in Figure 8. In some examples, process 1000 can be performed by any suitable apparatus or means to carry out the functions or algorithms described below.
[0089] [0089] In block 1002, a transmission device may use an SDAP entity to form an SDAP PDU including an SDAP header and an SDAP payload (e.g., IP payload) corresponding to one or more DRBs. The SDAP header can include information from the DRBs, for example, QFI and RQI of the QoS flows described above in relation to Figures 5 and 6. In block 1004, the transmitting device can form a PDCP PDU including a PDCP header and a PDCP payload that includes the SDAP PDU. The device can use processing circuit 740 to implement a PDCP entity that forms the PDCP PDU.
[0090] [0090] In block 1004, the transmission device can use the PDCP entity to encrypt only a portion of the PDCP payload. That is, the PDCP payload is partially encrypted. In one example, the PDCP entity can encrypt only the SDAP payload but not the SDAP header. In one aspect of the disclosure, the transmitting device can form a MAC PDU by adding an RLC header and a MAC header to encapsulate the PDCP PDU. Then, the transmitting device can use the DL 744 communication circuit or UL 844 communication circuit to transmit the MAC PDU to a receiving device.
[0091] [0091] The processes described above can be performed by a programming entity or a programmed entity. When the processes are carried out by the programming entity, the transmission can be a DL communication. When the processes are carried out by the programmed entity, the transmission can be a UL communication.
[0092] [0092] With reference to Figure 11, encryption is a process of changing information (data) to prevent an unauthorized recipient. Encryption involves the use of a 1102 data processing algorithm (encryption or encryption algorithm) that uses one or more secret or encryption keys that the sender and recipient use to encrypt and decrypt information. Decryption involves using a data processing algorithm 1104 to decrypt the data using the encryption key. In some aspects of disclosure, user plan data is encrypted at the PDCP layer to securely deliver IP packets to the user plan via DRB (s) over radio links.
[0093] [0093] When the SDAP header is unencrypted, certain optimizations can be implemented in the communication processes. For example, when a transmission device (for example, UE) has uplink data for transmission, the transmission device needs to decide on the amount of data for each logical channel to be included in a MAC PDU. When the transmitting device performs logical channel prioritization to prioritize data packets from different QoS streams, the MAC entity in the transmitting device can read the unencrypted SDAP header to make it even easier to prioritize data within a channel. logical. However, if the SDAP header is encrypted, then the MAC layer entity will be blind to that information, and the transmitting device will not be able to use that information for further data prioritization.
[0094] [0094] On the receiving side, when a device receives a MAC PDU, it removes or decodes all headers (for example, MAC header, RLC header, PDCP header, and SDAP header) and decrypts the header of SDAP if the SDAP header is encrypted by the transmitting device. However, if the SDAP header is unencrypted (unencrypted), the receiving device can read the contents of the SDAP header before decrypting the entire SDAP payload. As a result, the receiving device can perform certain pre-processing in advance, which increases the processing efficiency of the receiving device. For example, the receiving device can determine the RQI information so that the receiving device can configure the QoS-to-DRB mapping for the UL before completing the decryption of the SDAP payload.
[0095] [0095] Figure 12 is a flow chart illustrating an exemplary process 1200 for wireless communication on a receiving device using a packet structure with an unencrypted SDAP header in accordance with some aspects of the present disclosure. As described below, some or all of the illustrated features may be omitted in a specific implementation within the scope of this disclosure, and some illustrated features may not be necessary for the implementation of all modalities. In some examples,
[0096] [0096] In block 1202, the receiving device can receive a MAC PDU including a PDCP PDU that includes a PDCP header and a partially encrypted PDCP payload. In one example, the receiving device (for example, a programming entity 700) can use a UL 742 communication circuit to implement a MAC entity that receives the MAC PDU. In another example, the receiving device (for example, a programmed entity 800) can use a DL 842 communication circuit to implement a MAC entity that receives the MAC PDU.
[0097] [0097] In block 1204, the receiving device can extract an SDAP PDU corresponding to one or more QoS flows from the partially encrypted PDCP payload (for example, PDCP 618 payload in Figure 6). A partially encrypted PDCP payload includes at least one data field that is unencrypted. For example, the partially encrypted PDCP payload includes the SDAP PDU that includes an unencrypted SDAP header and an encrypted SDAP payload. For example, the receiving device may use the 740/840 processing circuit to implement various protocol entities to decode, extract, and / or decipher the MAC header, RLC header, PDCP header, SDAP header, and payload. useful SDAP of the MAC PDU.
[0098] [0098] In block 1206, the receiving device can read the SDAP header to obtain information on one or more QoS streams before deciphering the SDAP payload of the SDAP PDU. For example, the receiving device can use the 740/840 processing circuit to read information from the unencrypted SDAP header. Because the SDAP header is unencrypted, the receiving device can read the information (for example, QCF and RQI) before or while decrypting the SDAP payload. For example, the receiving device can determine a reflective QoS indicator (RQI) from the information obtained, and configure a mapping, based on the RQI, between a QoS flow and a DRB for an UL transmission before completing the transmission. decryption of the SDAP payload (for example, IP payload).
[0099] [0099] In a configuration, the device 700 and / or 800 for wireless communication includes means to carry out the various functions and processes described above. In one aspect, the aforementioned means may be the processor (s) 704/804 shown in Figure 7/8 configured (s) to perform the functions recited by the aforementioned means. In another aspect, the aforementioned means can be a circuit or any device configured to perform the functions recited by the aforementioned means.
[0100] [0100] Certainly, in the examples above, the circuitry included in the 704/804 processor is provided as an example only, and other means to perform the functions described can be included within various aspects of the present disclosure, including but not limited to instructions stored in the computer-readable storage medium 706/806, or any other suitable apparatus or means described in any of Figures 1, 2, 4, and / or 5, and using, for example, the described processes and / or algorithms here in relation to Figures 9 to 12.
[0101] [0101] Various aspects of a wireless communication network were presented with reference to an exemplary implementation. As people skilled in the art will readily appreciate, several aspects described throughout this disclosure can be extended to other telecommunications systems, network architectures and communication standards.
[0102] [0102] For example, several aspects can be implemented within other systems defined by 3GPP, such as Long Term Evolution (LTE), the Evolved Package system (EPS), the universal Mobile Telecommunication system (UMTS), and / or the Global System for Cellular (GSM). Several aspects can also be extended to systems defined by the 3rd Generation Partnership Project 2 (3GPP2), such as CDMA2000 and / or Optimized Evolution Data (EV-DO). Other examples can be implemented within systems using IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Ultra Broadband (UWB), Bluetooth, and / or other suitable systems. The actual telecommunication standard, network architecture, and / or communication standard used will depend on the specific application and the general design restrictions imposed on the system.
[0103] [0103] Within the present disclosure, the word "example" is used to mean "serving as an example, instance or illustration". Any implementation or aspect described herein as "exemplary" should not necessarily be interpreted as preferable or advantageous in relation to other aspects of the disclosure. Likewise, the term "aspects" does not require that all aspects of disclosure include the feature, advantage or mode of operation discussed. The term “coupled” is used here to refer to the direct or indirect coupling between two objects. For example, if object A physically touches object B, and object B touches object C, objects A and C can still be considered coupled to each other even if they do not touch each other directly physically. For example, a first object can be attached to a second object, even if the first object is never directly physically in contact with the second object. The terms "circuit" and "set of circuits" are widely used and are intended to include hardware implementations of electrical devices and conductors that, when connected and configured, allow the performance of the functions described in this disclosure, without limitation as to the type of electronic circuits , as well as software implementations of information and instructions that, when executed by a processor, allow the performance of the functions described in this disclosure.
[0104] [0104] One or more of the components, steps, characteristics and / or functions illustrated in Figures 1 to 12 can be reorganized and / or combined into a single component, step, characteristic or function or incorporated into several components, steps or functions. Additional elements, components, steps and / or functions can also be added without departing from the new features disclosed here. The apparatus, devices and / or components illustrated in Figures 1 to 12 can be configured to perform one or more of the methods, resources or steps described herein. The new algorithms described here can also be efficiently implemented in software and / or incorporated into hardware.
[0105] [0105] It must be understood that the specific order or hierarchy of steps in the disclosed methods is an illustration of exemplary processes. Based on the project's preferences, it is understood that the specific order or hierarchy of steps in the methods can be reorganized. The claims of the accompanying method present elements of the various steps in a sample order and are not limited to the specific order or hierarchy presented, unless specifically recited therein.
[0106] [0106] The above description is provided to allow anyone skilled in the art to practice the various aspects described here. Various changes in these aspects will be readily apparent to persons skilled in the art, and the generic principles defined herein can be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown here, but should be given the full scope consistent with the language of the claims, where the reference to an element in the singular is not intended to mean "one and only one" unless that is specifically indicated, but ”one or more”. Unless otherwise indicated, the term "some" refers to one or more.
A phrase referring to “at least one of” a list of items refers to any combination of those items, including unique members.
As an example, “at least one of: a, b or c” is intended to cover: a; B; ç; a and b; a and c; b and c; and a, b and c.
All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later known to those skilled in the art are expressly incorporated herein by reference and are intended to be covered by the claims.
In addition, nothing disclosed in this document is intended to be dedicated to the public, regardless of whether such disclosure is explicitly recited in the claims.

权利要求:
Claims (22)
[1]
1. A method of wireless communication in a transmission device, comprising: receiving one or more quality of service flows (QoS) from a protocol layer; map one or more QoS flows to one or more radio data carriers (DRBs) established between the transmitting device and a receiving device; and transmitting a plurality of media access control (MAC) protocol data units (PDUs) corresponding to one or more DRBs, each MAC protocol data unit (PDU) comprising: a data compression protocol PDU packet (PDCP) comprising a PDCP header and a partially encrypted PDCP payload.
[2]
A method according to claim 1, wherein the PDCP payload comprises: a service data adaptation protocol (SDAP) PDU comprising an SDAP header and an SDAP payload corresponding to one or more DRBs , where the SDAP header is unencrypted.
[3]
Method according to claim 2, wherein the payload of SDAP is encrypted.
[4]
A method according to claim 2, wherein the transmission comprises: reading the SDAP header from the partially encrypted PDCP payload to obtain SDAP payload prioritization information; and prioritize the transmission of the plurality of MAC PDUs based on the prioritization information.
[5]
5. Method, according to claim 4, in which prioritization comprises: prioritizing the transmission of MAC PDUs from the same logical channel based on the SDAP payload prioritization information in each MAC PDU.
[6]
A method according to claim 1, which further comprises: receiving a second MAC PDU comprising a second PDCP PDU comprising a PDCP header and a partially encrypted PDCP payload; extracting a second SDAP PDU corresponding to one or more second QoS streams, from the partially encrypted PDCP payload of the second PDCP PDU; and reading an SDAP header from the second SDAP PDU to obtain information on one or more second QoS streams before deciphering an SDAP payload from the second SDAP PDU.
[7]
A method according to claim 6, wherein the SDAP payload comprises an Internet protocol payload.
[8]
8. A method of wireless communication on a receiving device, comprising: receiving a media access control protocol (PDU) data unit (MAC) comprising a packet data compression protocol (PDCP) PDU comprising a PDCP header and a partially encrypted PDCP payload; extract a service data adaptation protocol (SDAP) PDU corresponding to one or more quality of service flows (QoS), from the partially encrypted PDCP payload; and reading an SDAP header from the SDAP PDU for information on one or more QoS streams before deciphering an SDAP payload from the SDAP PDU.
[9]
9. Method, according to claim 8, which further comprises: determining a reflective QoS indicator (RQI) from the information obtained; and configure a mapping, based on the RQI, between a QoS stream and a radio data carrier (DRB) for an uplink transmission (UL) before completing the decryption of the SDAP payload.
[10]
10. The method of claim 8, wherein extracting the SDAP PDU comprises: deciphering the SDAP payload while not deciphering the SDAP header.
[11]
A method according to claim 8, wherein the SDAP payload comprises an Internet protocol payload.
[12]
12. Apparatus for wireless communication, comprising: a memory that stores executable code; a transceiver configured for wireless communication; and a processor communicatively coupled with the memory and the transceiver, in which the processor and memory are configured to: receive one or more quality of service flows (QoS) from a protocol layer;
map one or more QoS flows to one or more data radio carriers (DRBs) established between the device and a receiving device; and transmitting a plurality of media access control (MAC) protocol data units (PDUs) corresponding to one or more DRBs, each MAC protocol data unit (PDU) comprising: a data compression protocol PDU packet (PDCP) comprising a PDCP header and a partially encrypted PDCP payload.
[13]
Apparatus according to claim 12, wherein the PDCP payload comprises: a service data adaptation protocol (SDAP) PDU comprising an SDAP header and an SDAP payload corresponding to one or more DRBs , where the SDAP header is unencrypted.
[14]
Apparatus according to claim 13, wherein the SDAP payload is encrypted.
[15]
15. Apparatus, according to claim 13, in which the processor and memory are still configured to: read the SDAP header from the partially encrypted PDCP payload to obtain SDAP payload prioritization information; and prioritize the transmission of the plurality of MAC PDUs based on the prioritization information.
[16]
16. Apparatus, according to claim 15, in which the processor and memory are still configured to: prioritize the transmission of MAC PDUs from the same logical channel based on the SDAP payload prioritization information in each PDU of MAC.
[17]
An apparatus according to claim 12, wherein the processor and memory are further configured to: receive a second MAC PDU comprising a second PDCP PDU comprising a PDCP header and a partially encrypted PDCP payload; extracting a second SDAP PDU corresponding to one or more second QoS streams, from the partially encrypted PDCP payload of the second PDCP PDU; and reading an SDAP header from the second SDAP PDU to obtain information on one or more second QoS streams before deciphering an SDAP payload from the second SDAP PDU.
[18]
An apparatus according to claim 17, wherein the SDAP payload comprises an Internet protocol payload.
[19]
19. Apparatus for wireless communication, comprising: a memory that stores executable code; a transceiver configured for wireless communication; and a processor communicatively coupled with the memory and the transceiver, in which the processor and memory are configured to: receive a media access control protocol (MAC) data unit (MAC) comprising a communication protocol PDU packet data compression (PDCP) comprising a PDCP header and a partially encrypted PDCP payload; extract a service data adaptation protocol (SDAP) PDU corresponding to one or more quality of service flows (QoS) from the partially encrypted PDCP payload; and reading an SDAP header from the SDAP PDU for information on one or more QoS streams before deciphering an SDAP payload from the SDAP PDU.
[20]
20. Apparatus, according to claim 19, in which the processor and memory are still configured to: determine a reflective QoS indicator (RQI) from the information obtained; and configure a mapping, based on the RQI, between a QoS stream and a radio data carrier (DRB) for an uplink transmission (UL) before completing the decryption of the SDAP payload.
[21]
21. Apparatus according to claim 19, wherein the processor and memory are further configured to: decipher the SDAP payload while not deciphering the SDAP header.
[22]
22. The apparatus of claim 19, wherein the SDAP payload comprises an Internet protocol payload.

类似技术:

公开号 | 公开日 | 专利标题

BR112020005692A2|2020-10-20|header formats in wireless communication

BR112020014058A2|2020-12-01|cellular unicast link establishment for vehicle-to-vehicle | communication

US20190320362A1|2019-10-17|Facilitating quality of service flow remapping utilizing a service data adaptation protocol layer

US10149213B2|2018-12-04|Group handover methods and systems

BR112020004707A2|2020-09-08|system and method for selecting resources to transmit beam failure recovery request

BR112019016421A2|2020-04-07|reuse of control resources for wireless data transmission

US10972937B2|2021-04-06|Group indicator for code block group based retransmission in wireless communication

BR112019025634A2|2020-06-23|STRATEGIC MAPPING OF UPLINK RESOURCES

US20190215693A1|2019-07-11|Service-based access stratum | security configuration

BR112019025530A2|2020-06-23|TRANSMISSION OF UPLINK CONTROL INFORMATION ON THE NEW RADIO

BR112019022026A2|2020-05-12|TRANSMISSION OF UPLINK CONTROL INFORMATION |

BR112020009678A2|2020-11-10|methods and devices for determining transport block size in wireless communication

BR112020000198A2|2020-07-07|uplink hop pattern modes for hybrid auto-repeat request | transmissions

US10986000B2|2021-04-20|Enabling new radio cellular quality of service for non-internet protocol data sessions

US10230502B2|2019-03-12|Hybrid automatic repeat request buffer configuration

BR112020020149A2|2021-01-05|SYSTEM AND METHOD THAT FACILITATES ROAMING DIRECTION

US20210337381A1|2021-10-28|Peer-to-peer link security setup for relay connection to mobile network

US20210297853A1|2021-09-23|Secure communication of broadcast information related to cell access

US20220038955A1|2022-02-03|Api-controlled pdcp out-of-order control and delivery for downlink traffic

WO2020068274A2|2020-04-02|User equipment based network-assisted scheduling for sidelink unicast communications

同族专利:

公开号 | 公开日

SG11202001306QA|2020-04-29|

TW201922015A|2019-06-01|

US10951533B2|2021-03-16|

KR20200053507A|2020-05-18|

CN111183672A|2020-05-19|

US20190097936A1|2019-03-28|

WO2019067107A1|2019-04-04|

JP2020535709A|2020-12-03|

EP3689020A1|2020-08-05|

引用文献:

公开号 | 申请日 | 公开日 | 申请人 | 专利标题

US6785236B1|2000-05-28|2004-08-31|Lucent Technologies Inc.|Packet transmission scheduling with threshold based backpressure mechanism|

FI20021869A0|2002-10-18|2002-10-18|Nokia Corp|A method and apparatus for transmitting packet data over a wireless packet data network|

KR100667700B1|2004-12-02|2007-01-12|한국전자통신연구원|Terminal of portable internet system and method of transmitting uplink data in terminal|

US9554417B2|2008-12-24|2017-01-24|Qualcomm Incorporated|Optimized header for efficient processing of data packets|

KR101703132B1|2015-06-12|2017-02-06|경북대학교 산학협력단|Markers for predicting pharmacodynamic response to imatinib and predicting method using thereof|

KR20180050192A|2016-11-04|2018-05-14|삼성전자주식회사|Structure of mac sub-header for supporting next generation mobile communication system and method and apparatus using the same|

US10349380B2|2017-03-17|2019-07-09|Ofinno, Llc|Radio access network area information|

EP3435700B1|2017-07-24|2020-09-16|ASUSTek Computer Inc.|Method and apparatus for serving quality of service flow in a wireless communication system|JP2020511842A|2017-03-24|2020-04-16|富士通株式会社|Network connection restoration method, device and communication system|

CN108810984B|2017-05-05|2020-03-24|维沃移动通信有限公司|Data processing method and device|

US11246183B2|2017-08-03|2022-02-08|Samsung Electronics Co., Ltd.|Method and apparatus for controlling access in next generation mobile communication system|

WO2019080034A1|2017-10-26|2019-05-02|Oppo广东移动通信有限公司|Data transmission method, terminal device and network device|

KR20190083944A|2018-01-05|2019-07-15|삼성전자주식회사|Method and apparatus for enhanced communication performance in a wireless communication system|

WO2019139376A1|2018-01-10|2019-07-18|Samsung Electronics Co., Ltd.|Method and apparatus for wireless communication in wireless communication system|

US20190349805A1|2018-05-11|2019-11-14|Mediatek Inc.|User equipments and methods for handling an update on quality of serviceflow to data radio bearermapping|

US10833799B2|2018-05-31|2020-11-10|Itron Global Sarl|Message correction and dynamic correction adjustment for communication systems|

CN110071935B|2019-04-30|2021-03-30|重庆邮电大学|Method for realizing SDAPhead assembly of terminal in 5G system|

CN110474924B|2019-09-17|2021-11-02|京信网络系统股份有限公司|Data transmission method and device, computer equipment and storage medium|

KR20210050398A|2019-10-28|2021-05-07|삼성전자주식회사|Electronic device for trnasmitting data to external electronic device not connected to the electronic device and method for the same|

US20220060930A1|2020-08-19|2022-02-24|Arris Enterprises Llc|Unilateral quality-of-service mirroring|

法律状态:
2021-11-23| B350| Update of information on the portal [chapter 15.35 patent gazette]|

优先权:

申请号 | 申请日 | 专利标题

US201762564113P| true| 2017-09-27|2017-09-27|

US62/564,113|2017-09-27|

US16/105,885|US10951533B2|2017-09-27|2018-08-20|Header formats in wireless communication|

US16/105,885|2018-08-20|

PCT/US2018/047378|WO2019067107A1|2017-09-27|2018-08-21|Header formats in wireless communication|

[返回顶部]